This is the RHQ 4.6 release. It was released on January 31st, 2013
RHQ 4.6.0 no longer has a GUI-based installer. Be sure to see TODO: PUT LINK HERE for updated installation and upgrade instructions.
The upgrade instructions should include a blurb like the following:
Due to a change in the JMS implementation, any unprocessed messages will be lost. To ensure messages are processed it is recommended to bring the server to maintenance mode for 2 minutes prior to stopping the server for the upgrade. Alternatively, all agents can be stopped and the server should continue to run for 2 minutes before shutdown. Note that a failure to do so will not endanger your upgrade, it means only that there is a slight chance of a missed alert.
If upgrading from RHQ 4.2 (4.3 and later are not affected) you must first make a manual change to your database. Have a look at the first note on the RHQ 4.4 release notes
RHQ 4.6 is recommended with Java7, and also supports Java6.
This is a significant infrastructure change. RHQ has migrated from AS 4.2.3 and now runs on AS7. There are many benefits associated with this update and several changes of note.
HornetQ replaces the dated JBoss Messaging implementation. There is one behavioral change for HA RHQ installations. Messages sent to a server must be delivered by that server. This means only that when a server goes down, any undelivered messages will not be delivered until that server returns to service. In the prior system messages could be delivered by other running HA nodes. In practical terms this will have little to no discernible effect.
The embedded agent is no longer functional with the RHQ Server now running inside JBossAS7. Its existence was of minimal benefit and the work to move it to the new platform was better directed elsewhere. Therefore, the embedded agent functionality has been completely removed.
Further enhancments
Alert definitions for resources can now be created, updates and deleted. THIS MAY CHANGE
BZ 896537: The Dashboard view now orders Dashboard Tabs alphabetically, guaranteeing order and allowing users to "land" on a non-default dashboard.
A new Cassandra plugin compatible with Cassandra 1.1.2 is part of this release. The plugin is still experimental but supports monitoring and configuration for the features exposed via Cassandra's JMX interface. Additional support for other internal configuration (Eg. gc_grace_seconds) has also been implemented.
The plugin is not yet compatible with Cassandra 1.2.x. A decision about support for Cassandra 1.2.x will be taken for the next RHQ release.
JAX-WS based Webservices have been removed. The REST interface, CLI and custom Java clients supersede the WS API.
Method org.rhq.core.util.exec.ProcessExecutor#redirectStreams has been deprecated. Callers should switch to using a new method org.rhq.core.util.exec.ProcessExecutor#redirectAllStreams method.
Method org.rhq.core.util.exec.ProcessExecutor#redirectStreams now returns void. This change restores the behavior of this method as it existed in RHQ 4.4.0 and prior. Clients that used the return type of the method introduced in RHQ 4.5.x and all the new code should use a new method called redirectAllStreams. The method redirectStreams has been deprecated as of RHQ 4.6.0 and will be removed in some future release.
Method org.rhq.core.domain.configuration.definition.PropertyDefinitionMap#getPropertyDefinitions() now returns a java.util.Map. This is to restore the behavior as it existed in RHQ 4.4.0 and prior.
Static fields org.rhq.core.domain.criteria.MeasurementScheduleCriteria#SORT_FIELD_* were removed. A few sort specifiers that were actually in error and if used would have produced a downstream error.
Number of arguments in the constructor of the class org.rhq.core.domain.alert.composite.AlertConditionAvailabilityCategoryComposite changed. While this class is available, it is not used directly in any of our remote APIs. The previous constructor signature was missing an argument required for correct behavior. See BZ 888927.
All the remote EJBs and handlers associated with the webservices were removed (WebServicesRemote, WebServicesTestRemote, RemoteWsInvocationHandler, ServerVersion).
The GWT part of the UI has partially been translated into German, Portuguese, Japanese, Chinese, Czech, Russian and Korean. The language should be automatically selected depending on your browser settings. You can explicitly access other translations by appending a locale specifier in the URL. For example to select the German translation you would append ?locale=de to the base URL, e.g. http://localhost:7080/coregui/?locale=de.
Supported locales are:
zh for Chinese
cs for Czech
de for German
ja for Japanese
pt for Portuguese
ru for Russian
ko for Korean
Please ping us if you want to help translating the UI to your language. Translations are done via the translations project on GitHub, which also has some instructions on how to start.
Please report all bugs you find in Bugzilla. If you find a bug that has been recorded in the above list, please leave a comment on them especially if this needs special steps to reproduce.
Please consult Bugzilla with a target release of RHQ 4.6.0 for a list of resolved issues
You can download the release here TODO: UPDATE THIS LINK!!!.